System and method for multi-angle videos

ABSTRACT

Systems, methods, and computer program products for cube graphical user interfaces are disclosed. A cube may be a two dimensional representation of a three dimensional object. The cube may contain a file or application on each face of the cube. The cube may be rotated such that a user may view the desired cube face. Each cube face may contain a single-angle video. The single-angle videos may be synchronized. A user may rotate the cube to view videos of an object or event from different angles.

FIELD

The present disclosure generally relates to graphical user interfaces (“GUI”), and more particularly to cubic GUIs for displaying digital video.

BACKGROUND

Graphical User Interfaces allow users to view and manipulate data on a screen. Data is typically displayed two dimensionally. The limited space on a screen limits the amount of data that can be displayed on a single screen. Moreover, users must often open multiple windows and layers of applications in order to use several different applications. Additionally, typical GUIs limit the communication between various applications.

Additionally, multiple users of a computer or program may desire different content and appearances for the system. Switching users may require a restart of a computer, or otherwise take time for new profile to load. Faster, more user friendly systems for changing profiles may be desired.

Furthermore, users often transmit multiple files between each other as attachments to a communication such as an email or message. However, it can be time consuming to individually attach each file to the message, as well as to download each file separately. Zip files are one method of transmitting multiple files. However, these files do not allow recipients to easily view the contents of the zip file and decide which files to download.

Additionally, video is typically presented to users without giving users the ability to select a desired camera angle. Although camera angles may change throughout a video, the user is limited to the camera angle selected by the video provider. Thus, users are not able to control the video viewing experience by easily changing between camera angles.

SUMMARY

The present disclosure includes a system, method and computer program product for using cubes as three dimensional graphical user interfaces (“GUI”). In various embodiments, a cube may comprise a container on each cube face. One or more files or applications may be loaded into each container. The cube may be rotated to display a selected cube face. The cube configuration may be saved, such that the files or applications on each cube face are saved on the cube.

In various embodiments, systems, methods and computer program products for changing profiles using a cube are disclosed. A profile cube may comprise a user profile on one or more cube faces. A first cube face may comprise a first user profile and a second cube face may comprise a second user profile. The different user profiles may correspond to different users. However, in various embodiments, the different user profiles may correspond to different profiles for the same user. In response to the profile cube being rotated from the first cube face to the second cube face, at least one of the content and display of the screen may change to settings associated with the second user profile. The user profiles may include sub-profile cubes which allow users to further specify settings for multiple profiles of the same user.

In various embodiments, systems, methods and computer program products for transmitting files using a cube are disclosed. A cube may be created. Each cube face may be associated with a file or application. The cube may be compressed and transmitted to a recipient. The compressed cube may be transmitted as an email attachment. The recipient may request to resize the cube, and uncompressed data may be transmitted to the recipient in order to display the resized cube.

In various embodiments, systems, methods and computer program products for analyzing data using a cube are disclosed. Graphical data may be associated with multiple cube faces of an analytic cube. The data may be merged such that data lines extend through the cube in three dimensions. The three dimensional data may assist in determining a relationship between the data. A target goal may be created within the analytic cube. A data line may be moved to intersect with the target goal. The analytic cube may determine requirements in order to meet the target goal.

In various embodiments, systems, methods and computer program products for creating and displaying multiple angles of video using a cube are disclosed. Each cube face may comprise a different single-angle video. The single-angle videos may be of the same object or event. The single-angle videos may be synchronized. By rotating the cube, different angles of the same object or event may be viewed.

In various embodiments, a method may include generating a multi-angle video object (“MAV”). A first video may be displayed on a first face of the MAV. A second video may be displayed on a second face of the MAV. The MAV may be rotatable between the first face and the second face.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding may be derived by referring to the detailed description and claims when considered in connection with the Figures, wherein like reference numbers refer to similar elements throughout the Figures, and:

FIG. 1 illustrates a cube according to various embodiments of the disclosure;

FIG. 2 illustrates a profile cube according to various embodiments;

FIG. 3 illustrates a plurality of cubes including a profile cube according to various embodiments;

FIG. 4 illustrates a full size cube and a compressed cube according to various embodiments;

FIG. 5 illustrates a process for transmitting a compressed cube according to various embodiments;

FIG. 6 illustrates an analytic cube according to various embodiments;

FIG. 7 illustrates a synchronized camera system according to various embodiments;

FIGS. 8A-8D illustrate various views from a synchronized camera system according to various embodiments; and

FIG. 9 illustrates a system for creating and utilizing cubes according to various embodiments.

DETAILED DESCRIPTION

The detailed description of exemplary embodiments herein makes reference to the accompanying drawings and pictures, which show various embodiments by way of illustration. While these various embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.

Systems, methods and computer program products are provided. In the detailed description herein, references to “various embodiments,” “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.

Graphical User Interfaces (“GUI”) including cubes are disclosed according to various embodiments. Although described herein with reference to cubes, the present disclosure is compatible with any shape of objects, such as tetrahedrons and decahedrons. In various embodiments, a cube may be presented to a user. The cube may be a two-dimensional graphical representation of a three-dimensional cube. However, in various embodiments, three-dimensional cubes may be used with three-dimensional displays.

In various embodiments, the user may rotate the cube. The user may click on and drag the cube such that it rotates. In various embodiments, in response to the user clicking on an edge of the cube, the cube may rotate such that a cube face adjacent to the edge is rotated to the front of the display. In various embodiments, the cube faces are transparent or semi-transparent, such that all cube faces are displayed simultaneously. In various embodiments, the cube faces may become transparent or semi-transparent in response to a user moving a mouse to a specified location, such as a specified distance from an edge of the cube. The cube may further comprise a key or legend which displays what is located on each cube face. Thus, the user may select an item in the key and the cube may rotate such that the cube face corresponding to the selected item is rotated to the front of the cube. The user may select any of the cube faces by clicking on a cube face, and the cube may rotate such that the selected cube face is moved to the front.

In various embodiments, the cube may maintain the orientation of the content on a cube face relative to that cube face. In response to a user selecting a cube face adjacent to a currently displayed cube face, the cube may perform a first rotation of ninety degrees in a first direction in order to display the selected cube face. However, if the content of the selected cube face is not oriented correctly (e.g. upside down or sideways), the cube may also perform a second rotation of ninety or one hundred eighty degrees in a second direction in order to orient the content of the selected face correctly. In various embodiments, the first rotation and the second rotation may be performed simultaneously.

In various embodiments, the cube may rotate to display the selected cube face, and the content of the selected cube face may be rotated to the correct orientation without rotating any other portion of the cube. Thus, only one rotation of the entire cube may be required, and the content may still be displayed correctly.

Each cube face may comprise a container capable of holding one or more files. The user may add a file to a cube face by dragging and dropping a file onto the cube face. In various embodiments, the user may load a file onto the cube face by browsing through files and selecting a file to be loaded onto the cube face. In various embodiments, the cube and/or the cube face is not limited to a particular application. Thus, the user may select any type of file or application and load it onto the cube face. Furthermore, the user may load different application files to each cube face. For example, a user may load a text file on a first cube face, and a web browser on a second cube face.

In various embodiments, each cube face may comprise a single file or application. However, in various embodiments, each cube face may comprise a plurality of files and/or applications. Furthermore, in various embodiments, a cube face may comprise one or more smaller, second level cubes. Each second level cube may comprise one or more files or applications on each cube face of the second level cube. Second level cubes may comprise third level cubes, etc. In various embodiments, the multiple levels of cubes may be organized similar to a folder structure or a drill-down menu.

In various embodiments, the user may save cube configurations. The user may load particular files on the cube faces, and save the cube configuration. The user may open the saved cube configuration at a later time, and the cube configuration may open with all of the files saved on the cube faces. Furthermore, the cube may load dynamically, such that if a user has updated one of the files by working on the file individually in its native application, the file may automatically update on the saved cube. In various embodiments, cube configurations comprising a plurality of applications may be saved. For example, a user may save a cube with a text editor on a first cube face, a web browser on a second cube face, and a multimedia player on a third face.

In various embodiments, cube configurations may be sold as software bundles. Software developers may determine that certain programs are often used in combination with each other, and may package such software together on a cube. The software manufacturer may be able to provide discounts to the consumer by selling multiple applications together. Additionally, certain software programs require a networking effect in order to become popular, and by bundling software which requires a networking effect on a cube with already popular software, developers may increase the speed of distribution of new programs.

In various embodiments, users may create custom cube configurations which can be sold user-to-user. The cube software developer may take a royalty from user-to-user sales. Thus, the cube software developer may be able to encourage users to create more useful or otherwise desirable cube configurations and profit from the creations.

The cube may comprise an active face which is visible on a display. In read-only situations, the user may view whatever information is on the active cube face. The user may resize the cube and perform operations typically associated with read-only documents. In various embodiments, a user may save a cube configuration as read-only. The cube may be saved in a common format, such as .pdf or .jpg. Thus, the read-only cube may be viewed on systems which are not capable of running various software applications which were used to create the files on the cube faces. For example, a first user may create a cube comprising .doc files and save the cube as read-only. A second user may download the cube. However, the second user's system may not be capable of displaying .doc files. The cube may convert the files to .jpg so that the second user may view the files on the cube. In various embodiments, the cube may comprise partial applications that allow the second user to view the files in their native format on the cube without requiring the second user's system to be capable of displaying .doc files.

In various embodiments, a plurality of cubes may be present on a screen. The plurality of cubes may interact with each other, and/or be separately functioning cubes. In various embodiments, each cube may exist in its own plane. Thus, one or more cubes may overlap without affecting the functionality of each other. In various embodiments, a plurality of cubes may exist in each plane.

Referring to FIG. 1, a plurality of cubes are illustrated according to various embodiments. Cube 100 comprises a text document on a first cube face 110, a slide show document on a second cube face 120, and a spreadsheet document on a third face 130. As illustrated by the arrows, cube 100 may be rotated to display the different cube faces.

Cube 150 may comprise a software bundle. Cube 150 may comprise a text editor application on a first cube face 160, a slide show application on a second face 170, and a spreadsheet application on a third face 180. In various embodiments, a user may create cube 100 by dragging and dropping files onto cube 150. However, in various embodiments, a user may open files from within the cube faces of cube 150. In various embodiments, a user may change which applications correspond to the various cube faces of cube 150.

In various embodiments, a display profile may be selected based on an active face of a profile cube. The profile cube may comprise a variety of profiles. In various embodiments, the profiles may be associated with a specific user. For example, a first cube face may be associated with a first user, and a second cube face may be associated with a second user. Each user may fully customize the display and content of their associated profile.

For example, the first user profile may comprise icons and applications which the first user has selected. Additionally, each user may have several sub-profiles which are associated with the user. The sub-profiles may be selected from a separate sub-profile cube from the profile cube. In various embodiments, the sub-profile cube may be embedded within the profile cube. In response to a profile being selected from the profile cube, the sub-profile cube associated with the profile may be displayed. The sub-profile cube may allow the user to select various sub-profiles. For example, in various embodiments, the first user's sub-profiles may be associated with different subjects in school, such as Math, English, and History.

In response to a sub-profile being selected, the displayed content may change to content associated with the sub-profile. In various embodiments, in response to the Math sub-profile being selected, math related cubes, folders, files, and/or applications may be displayed to the user. In various embodiments, a Math cube associated with the Math sub-profile may be displayed. The Math cube may comprise applications and documents often used by the user while in the Math sub-profile. For example, a first cube face may comprise a web browser connected to a homepage for a math class, and a second cube face may comprise a calculator application. One skilled in the art will recognize that any documents or applications may be compatible with the present disclosure.

In various embodiments, the layout of a desktop or dashboard may be based on the active profile. Various icons on a desktop may change based on the active profile. Additionally, settings such as colors, themes, icon sizes, etc. may be saved in association with particular profiles. In various embodiments, the profile cube may fill the entire display of a screen. However, in various embodiments the user may minimize the profile cube, and the profile cube may be displayed in a task bar or other location on the screen.

Referring to FIG. 2, various views of a profile cube 200 are illustrated according to various embodiments. Profile cube 200 may comprise a profile for a first user on a first cube face 210. Profile cube 200 may further comprise a profile for a second user on a second cube face 220, and a profile for a third user on a third cube face 230. The illustrated profiles may correspond to different students. However, in various embodiments, the profiles may correspond to any users, or to different sub-profiles of a single user. By rotating profile cube 200, different profiles may be selected.

In various embodiments, in response to a profile being selected, a desktop or dashboard may change the display to correspond to settings of the selected profile. As illustrated in FIG. 2, in various embodiments, the cube faces on profile cube 200 may further comprise categories, such as grades, profile, settings, etc. In various embodiments, in response to a user selecting a category, a second cube may open corresponding to the selected category. However, in various embodiments, in response to a user selecting a category, the selected category may populate the first cube face 210 of the profile cube 200. For example, in various embodiments, the first cube face 210 of the profile cube 200 may be active, and the user may select the grades category. The first cube face 210 may display information relating to the grades of the first user. For example, the first cube face 210 may display the grades for the first user for each class the first user attends. The user may further be able to select one of the classes, and a more detailed breakdown of the specific class may be displayed on the first cube face 210.

Referring to FIG. 3, a display comprising a plurality of cubes including a profile cube 310 is illustrated according to various embodiments. The display may further comprise an application cube 320 and an analytic cube 330. Profile cube 310 may comprise a plurality of profiles. In response to a user rotating profile cube 310 to a different active profile, one or more of the plurality of cubes may change the content to display content associated with the active profile. In various embodiments, in response to a user rotating cube 310 to a different active profile, the plurality of cubes may be replaced by a plurality of cubes associated with the active profile. In various embodiments, a first subset of the plurality of cubes may change in response to profile cube 310 rotating, and a second subset of the plurality of cubes may remain the same.

In various embodiments, a user may transmit a cube to a recipient. In various embodiments, the cube may be attached to an email as an attachment. A user may load a plurality of files onto a cube and therefore transmit several files as a single cube attachment. Unlike a zip file, the recipient may receive the cube and choose to open individual files on the cube faces without downloading the entire cube. The user may compress the cube prior to sending the cube in order to minimize the time and data required for the transmission.

In various embodiments, cubes may be created, edited, and/or stored on cloud computing networks. A user may upload files via a website and use the files to create cubes by adding the files to cube faces. The user may transmit cubes which are stored on the cloud to a recipient. The transmitted cubes may be compressed to minimize the time and/or data for the transmission. In various embodiments, the transmitted cube may contain links to files or cubes stored on the network, rather than the actual files or cubes themselves. The user may modify the cube or files on the cube even after the cube has been sent to the recipient, and the recipient may view the latest version of the cube when opening the cube.

In various embodiments, the recipient may receive a compressed cube. The recipient may view the various files associated with the compressed cube by rotating the compressed cube. If the recipient wishes to view or save the cube in an uncompressed, or less compressed format, the recipient may resize the cube. The recipient web client may transmit a message to the system indicating that the cube is being resized. The system may transmit the uncompressed data in order for the full sized cube to be available to the recipient.

In various embodiments, the recipient may resize the cube to any dimensions, and based on the dimensions, the system may transmit data compressed to fit the resolution of the resized dimensions. In various embodiments, the data may be transmitted dynamically and/or continuously, such that as the recipient resizes the cube, data is transmitted to the user web client based on the current cube size. Thus, it may appear to the user that the user is simply stretching the cube locally. However, unlike a compressed object being simply stretched, where resolution is diminished, the data transmitted by the system will maintain the resolution of the cube as it is resized.

In various embodiments, in response to the cube being resized, data for the enlarged cube is transmitted for only the active cube face. Thus, the system is not required to transmit data for the entire cube if the recipient is only viewing one cube face. In response to the recipient rotating the cube such that a second cube face becomes the active cube face, the system may transmit data associated with the second cube face. However, in various embodiments, the system may transmit data for the entire cube in response to the cube being resized.

In various embodiments, a user may decide how much to compress a cube prior to sending. Referring to FIG. 4, a full size cube 410 and a compressed cube 420 are illustrated according to various embodiments. The user may select a corner of full size cube 410 and drag the corner in order to compress the full size cube 410 down to compressed cube 420. In the illustrated embodiment, the full size cube 410 is compressed from 1 GB to 500 MB. However, one skilled in the art will appreciate that cubes may be compressed to any size. A user may download, email, share, or otherwise use compressed cube 420 for any purpose. Thus compressed versions of the data of full size cube 410 may be transmitted or used without requiring the full amount of data on full size cube 410 to be transmitted.

In various embodiments, a cube web application is disclosed. Users may create an account on the cube web application. The user may login to the account with a username and password. The account may allow the user to create or upload various cubes. In various embodiments, a user may upload files to an online library. The user may select files from the online library to be inserted into a cube. The user may store a plurality of cubes in the account. The user may create albums to store the plurality of cubes. For example, the user may create photo cubes which comprise a photo on each cube face, and store the photo cubes in a photo album.

Cubes may be shared with third parties via a variety of methods. For example, a user may select a cube to be shared and may send the cube to a recipient via email, SMS, or any other method. Additionally, users may embed the cubes into social media messages or postings. The user may post a compressed cube, or a link to a cube, on a social media site. Those wishing to view the cube in full size may download the cube, or may resize the cube, in which case a less compressed version of the cube may automatically download.

In various embodiments, the user may implement security features in order to protect the cube, and/or one or more cube faces. For example, the user may password protect a first cube face. Third parties may view or download the cube. However, the third party may be required to enter a password in order to view or edit the first cube face. In various embodiments, multiple cube faces may be protected by different passwords.

In various embodiments, the cube faces may interact in order to unlock various cube faces. For example, a first cube face may comprise an assignment, and in response to a user completing the assignment, the first cube face may display a password which may be used to unlock a second cube face. In various embodiments, the second cube face may automatically unlock in response to the user completing the assignment on the first cube face.

Referring to FIG. 5, a process for creating and transmitting cubes is illustrated according to various embodiments. In step 510, a cube server creates a cube. In various embodiments, the cube server may create a blank cube. In step 520, the cube server associates data with each cube face of the cube. In various embodiments, the data may be files or applications. In various embodiments, a user may select data stored on a database to be associated with the cube faces. However, in various embodiments, a user may upload a preconfigured cube. In step 530, the cube server may compress the cube. In various embodiments, the cube server compresses the cube to a predetermined size. However, in various embodiments, the cube server compresses the cube to a size indicated by the user.

In step 540, the cube server transmits the compressed cube to a recipient. The recipient may view the compressed cube and determine whether the recipient desires to view one or more cube faces in a larger size. In step 550, the cube server may receive a request from the recipient to view the cube in a larger size. In various embodiments, the request may be to view the full size cube. However, in various embodiments, the request may be to view the cube in any size between the full size cube and the compressed cube. In step 560, the cube server may transmit data to display the cube in the larger size.

In various embodiments, cubes may be used for analytics. A first cube face of an analytic cube may comprise a graph. The graph may comprise any type of data. For example, in various embodiments, the graph may comprise a student's level of mastery of a subject over time, for example the student's level of mastery of Math. A second cube face may comprise a second graph. The second graph may comprise the student's level of mastery of English over time. A single cube may thus represent a student's progress in multiple subjects. In various embodiments, one or more graphs may be presented on each cube face.

In various embodiments, the various graphs and/or data on the cube may be displayed three-dimensionally, such that the data appears within the analytic cube. The data from the various cube faces may be merged together, such that relationships between the data may be established. In various embodiments, the user may drag one or more graph in order to create an intersection point between the graphs. The user may create a target goal in the cube. The target goal may represent a desired level of mastery for a subject.

In various embodiments, the graph data may represent a plurality of assignments which must be completed in order to achieve a proficiency level. In response to the user manipulating the graph, the analytic cube may populate a calendar with the plurality of assignments. For example, the graph may initially indicate that ten assignments are required in order to reach a particular point representing a proficiency level on the graph in ten days. The ten assignments may be calendared one per day on the calendar. In response to the user adjusting the graph such that the student should reach the same point on the graph within five days, the ten assignments may be calendared two per day on the calendar.

By merging the data, the system may display a relationship between the various graphs. For example, the graphs may indicate that a student must improve their proficiency in English by a specified amount in order to increase their proficiency in Math. Thus, rather than looking at each subject in a vacuum, the analytic cube may indicate that a deficiency in one subject is causing or otherwise related to a deficiency in another subject.

Referring to FIG. 6, an analytic cube 600 is illustrated according to various embodiments. Analytic cube 600 may comprise a first cube face 610, a second cube face 620, and a third cube face 630. A user may import data onto the various cube faces. For example, in the illustrated embodiment, skills assessment data for a student may be loaded onto first cube face 610, reading data may be loaded onto second cube face 620, and math data may be loaded onto third cube face 630. In various embodiments, data may be loaded onto each face of the cube. In various embodiments, analytic cube 600 may merge the data, such that the data extends in three dimensions through analytic cube 600, for example by displaying data line 615. In various embodiments, the user may insert target goal 640 into analytic cube 600. Target goal 640 may represent a desired skill level for the student. However, target goal 640 may represent any data point for any data set. In various embodiments, a user may drag data line 615, or any other data line or point, to intersect target goal 640. In response, analytic cube 600 may calculate and transmit data indicating necessary requirements in order for the student to meet target goal 640.

In various embodiments, cubes may be used in conjunction with conference calls and/or video calls. For example, each participant of a conference call may be represented on a cube face. A user may rotate the cube to view a particular participant. In various embodiments, the user may only be able to send and/or receive communications from the participant on an active cube face. For example, a first cube face may comprise all participants in the call, and the user may communicate with all users simultaneously in response to the first cube face being active. However, the user may rotate the cube to a second cube face comprising a first participant, and the user may only communicate with the first participant in response to the second cube face being active. In various embodiments, files may be uploaded onto a cube face, and the file may be displayed to the other participants on the call. In various embodiments, empty cube faces may be used to dial new participants, or to upload files. In various embodiments, the first cube face may comprise all participants in the call, and in response to the user selecting the first participant on the first cube face, the cube may rotate to display the first participant.

In various embodiments, cubes may provide users with a multi-angle viewing experience. One or more sides of a cube may represent a single-angle video. For example, in various embodiments, each side of the cube may show a video from a different angle of the same object. In various embodiments, a cube may represent a point-of-view perspective, such that each side of the cube represents a video of a different view from the same point-of-view. This may provide a three-dimensional viewing experience for the user.

In various embodiments, a multi-angle video object (“MAV”) may comprise a plurality of faces. In various embodiments, the MAV may comprise a cube, and the plurality of faces may comprise a front face, a rear face, a left face, a right face, a top face, and a bottom face. However, the MAV may comprise the shape of any three-dimensional object. Front face may display a video of an object or event from a front view. Left face may display a video of the object or event from a left view. Similarly each face may display a video of the object or event from a respective view. Each face may comprise tools associated with viewing a video. For example, each face may comprise controls such as play, pause, fast forward, rewind, stop, zoom in/out, volume adjustment, etc. A user may watch the video from different angles by rotating the MAV as previously described with respect to cubes. In various embodiments, the user may watch multiple angles simultaneously by partially rotating the MAV, such that multiple sides of the MAV may be seen simultaneously.

In various embodiments, the single-angle videos may be synchronized. In various embodiments, the single-angle videos may have been recorded at the same time. Thus, additional synchronization may not be necessary in order to allow a user to switch between video angles while maintaining temporal consistency. However, in various embodiments, the starting recording time for the single-angle videos may be offset, and synchronization may be performed. In other words, a camera at a first angle may have begun recording an event prior to a camera at a second angle, and without additional synchronization, the timeline of a video may appear inconsistent in response to a user changing views of a MAV.

In various embodiments, synchronization of a MAV may be performed manually. A user may mark a synchronization baseline in a first angle. In various embodiments, the synchronization baseline may be visual or audio. For example, a video may display a person clapping their hands once. On a front face of a MAV, a front-angle video may show the person's hands making contact from the clap at 11 seconds from the start of the front-angle video. The user may mark the moment of contact from the clap for synchronization. The user may rotate the MAV to a right side face, which may display a right-angle video of the clap. In the right-angle video, the moment of contact from the clap may occur at 17 seconds from the start of the right-angle video, because a camera recording the right-angle video may have begun recording 6 seconds before a camera recording the front angle video. The user may mark the right-angle video for synchronization at the moment of contact from the clap. Based on the user's marks, the right-angle video may be time-shifted by six seconds such that the clap occurs at the same time in both the front-angle video and the right-angle video.

In various embodiments, synchronization may be automatic. The system may search for a distinctive sound or visual cue in the single-angle videos, and the system may time-shift the single-angle videos such that the distinctive sound or visual cues align in the single-angle videos. In various embodiments, the single-angle videos may comprise metadata regarding the time that the single-angle videos were recorded, and the system may use the metadata to synchronize the single-angle videos. In various embodiments, the user may select a “synchronize” feature, and the system may automatically synchronize the videos.

In various embodiments, a user may desynchronize the time-sequence of the videos. Thus, the user may change the time position of a video of one single-angle without altering the time position of the other single-single angle videos. For example, a user may wish to watch a portion of a video from multiple angles. The user may desynchronize the videos at the beginning of the desired portion. The user may watch the portion from a first angle. The user may rotate the multi-angle cube to a second angle, and because the single-angle videos were desynchronized, the user may play the video from the second angle from the time location where the single-angle videos were desynchronized (e.g. the beginning of the desired portion) without requiring the user to rewind or otherwise search for the beginning of the desired portion. In various embodiments, the user may resynchronize the single-angle videos at any time. The single-angle videos may be synchronized to an active cube face. In various embodiments, the single-angle videos may be resynchronized to the last time location where the user desynchronized the single-angle videos.

In various embodiments, the cube server may normalize the single-angle videos. For example, the cube server may adjust settings such as brightness, contrast, volume levels, zoom settings, video dimensions, resolution, etc. in order to make the different single-angle videos appear more consistent than the raw videos, even though the single-angle videos may have been shot under different conditions and using different equipment.

In various embodiments, only one MAV face may play a video at a time. The user may rotate the MAV from a first face to a second face, and transition point may be determined. The transition point may be the temporal location of the video on the first face at the time the user rotates the MAV. In response to the user rotating the MAV, the cube server may stop playback of the video on the first face at the transition point, and the cube server may begin playback of the video on the second face at the transition point. Thus, playback of the video may appear to be seamless in response to transitioning to different views on different faces, even though only one MAV face plays a video at any given time.

In various embodiments, as many as all MAV faces may simultaneously play video. Thus, in response to the user rotating the MAV, there may be no need to determine a transition point. Although a subset of the MAV faces may be hidden from the user, the MAV faces may continue to play video in the background.

In various embodiments, a MAV may be an interior MAV. An interior MAV may comprise single-angle videos taken from a central point of view, such that the user appears to be located in the interior of the cube. For example, a car may comprise a camera pointed forward of the car, a camera pointed rearward from the car, a camera pointed to the left of the car, a camera pointed to the right of the car, a camera pointed to the ground below the car, and a camera pointed to the sky above the car. Each camera may record a single-angle video which may be viewed on a cube face. Thus, by rotating between the various cube faces, the user may be able to experience the viewpoint of the driver of the car.

In various embodiments, a MAV may be an exterior MAV. An exterior MAV may comprise single-angle videos taken of the same object or event from different angles, such that the user may appear to be transported to different viewpoints in response to rotating the MAV.

Multi-angle video shapes are described primarily with references to cubes. However, in various embodiments, a multi-angle video shape may comprise any three-dimensional shape, such as a tetrahedron, octahedron, dodecahedron, etc. In various embodiments, a multi-angle video shape may comprise a side for each available video angle. Each video angle may be represented by a surface orthogonal to the video angle. In various embodiments, a MAV may comprise an irregular shape, and in various embodiments, a MAV may comprise an open shape, wherein the MAV comprises at least one face with a side not connected to another face, as opposed to a closed shape, wherein each side of each face is connected to another face.

In various embodiments, a MAV may be flattened. Flattening the MAV may enable the user to view all or some of the single-angle videos on the MAV simultaneously. For example, in response to a user flattening a MAV cube, a screen may be split into six frames, with each frame displaying one of the single-angle videos. In various embodiments, the user may select a subset of the single-angle videos to be displayed in the flattened view.

In various embodiments, a MAV may be compatible with any type of video file. For example, in various embodiments, the MAV may be compatible with .MPG, .MOV, .WMV, .RM, or any other video file types. In various embodiments, a new codec, such as “.3VI” may be created which stores a plurality of single-angle videos in a multi-angle video file. The .3VI file may comprise information about the single-angle videos, such as the relative angles of each single-angle video. For example, each single-angle video may be associated with a “front,” “left,” “right,” “rear,” “top,” or “bottom” angle. Thus, MAVs comprising multiple video angles may be stored or transferred in a single file.

In various embodiments, a user may create a MAV. The user may upload single-angle videos to a cube server. In various embodiments, the cube server may comprise previously existing videos. The user may select a first single-angle video to place on a first side of the MAV. In various embodiments, the user may designate the first single-angle video as a particular angle, such as a front view. In various embodiments, based on the designation, the cube server may select an appropriate side of the MAV for the first single-angle video. However, in various embodiments, the user may manually select a side of the MAV for the first single-angle video. The user may continue adding single-angle videos to the MAV.

In various embodiments, the number of single-angle videos the user may add to the MAV may be limited by the shape of the MAV. For example, in embodiments where the MAV is a cube, the user may be limited to adding six single-angle videos to the MAV, as the MAV cube has six sides. However, in various embodiments, the user may continue add as many single-angle videos as desired to the MAV. In response to the user indicating that all desired single-angle videos have been added to the MAV, the cube server may create a MAV based on the number of single-angle videos added to the MAV. In various embodiments, the MAV may comprise one side for each single-angle video. As the number of single-angle videos increases, the area of each face of the MAV becomes smaller relative to the total surface area of the MAV. As the number of single-angle videos approaches extremely large numbers, the MAV may be substantially spherical. Thus, a user may rotate the MAV to achieve nearly any viewpoint.

In various embodiments, synchronized camera systems (“SCS”) may be utilized to create MAVs. For example, for an interior MAV, a plurality of cameras may be coupled to an object, such as a person or a vehicle, pointing in different directions, such as front, rear, and side angles. The SCS may contain data for each camera indicating the angle of each camera. Thus, an operator may instruct the SCS to record, and the SCS may record various views from the object. The SCS may create a single digital file comprising all of the recorded views, such as a .3VI file, which may be viewed using a MAV without requiring the user to create a MAV using individual single-angle videos. In various embodiments, SCS may capture video which may be streamed live. Thus, users may select multiple angles of live events.

In various embodiments, an SCS may comprise detailed locational data for each camera in the SCS. For example, the SCS may record the GPS location of each camera, the compass angle of each camera, the declination (angle relative to horizon) of each camera, and any other available information. The SCS may utilize such locational data in creating the .3VI file, such that an appropriately shaped MAV may be created regardless of camera locations, without a user having to manually reconfigure a MAV each time one or more cameras is moved.

Referring to FIG. 7, an exterior SCS 700 is illustrated according to various embodiments. Exterior SCS 700 may comprise a plurality of cameras 760A, 760B. In various embodiments, SCS 700 may comprise one or more cameras 760A corresponding to one or more cube faces 770. In various embodiments, SCS 700 may comprise one or more cameras 760B corresponding to one or more cube edges 780 or cube corners 790. In various embodiments, cameras 760B may be utilized in combination with or independent of cameras 760A. In the illustrated embodiment, exterior SCS comprises a camera 760A corresponding to each cube face 770, and a camera 760B corresponding to each cube edge 780, for a total of 18 cameras. Thus, a user watching a video created by SCS 700 may rotate between 18 different video angles. Although exterior SCS 700 is illustrated as an exterior SCS with cameras 760A, 760B recording a location within exterior SCS 700, cameras 760A, 760B may be directed to point away from a center of exterior SCS 700, thus changing exterior SCS 700 into an interior SCS.

In various embodiments, single-angle videos may be stitched together. Stitching the single-angle videos together may give users the ability to move to any angle, including angles between camera positions. In various embodiments, the single-angle videos may be stitched frame by frame, similar to stitching of panoramic photographs.

In various embodiments, in response to the user changing camera angles, one or more transitory images may be displayed as the user switches between camera angles. For example, a midpoint transitory image may comprise an average color and/or brightness for each pixel of a first camera angle and a second camera angle. In response to the user changing camera angles, the midpoint transitory image may be briefly displayed, which may create the illusion of the camera moving from the first camera angle to the second camera angle. In various embodiments, a plurality of transitory images may be displayed between the first camera angle and the second camera angle.

In various embodiments, cameras 760A, 760B may record raw photon and material properties of an image. The returned light level and energy may be recorded from various camera angles. Thus, an output color and focal point of an image may be calculated for various positions between camera angles. Focal points, depth of field, and light levels may be defined based on the recorded data. The angles of the photons recorded from each camera 760A, 760B may be utilized to generate images from angles between camera angles. Thus, the user may select an angle between camera angles.

Referring to FIGS. 8A-8D, various views from single-angle videos are illustrated according to various embodiments. FIG. 8A illustrates a Left view 810 of an acrobat 800. A user may play, pause, fast forward, or perform other standard video functions of Left view 810. Additionally, a user may rotate the video to view a different angle corresponding to a different single-angle video. For example, the user may rotate the video by selecting on a right side of Left view 810 and dragging a selector, such as a mouse, to the left. This may cause the view to rotate to a Rear view 820 as shown in FIG. 8B. The user may rotate the video to various angles. For example, the user may rotate the video in the same direction to view a Right view 830 as shown in FIG. 8C. The user may also rotate the video up or down. For example, the user may select the bottom of the video and display a Bottom view 840 as illustrated in FIG. 8D.

Referring to FIG. 9, a system 900 for displaying, transmitting, and/or utilizing cubes is illustrated according to various embodiments. System 900 may comprise cube server 910, cube database 920, web client 930, and network 940. Cube server 910 may comprise any single server or combination of servers capable of creating, displaying, transmitting, and/or utilizing cubes. Cube server 910 may communicate with database 920 in order to retrieve stored information. Database 920 may comprise any database or combination of databases capable of storing information which may be accessed by cube server 910. Web client 930 may be any device, such as a personal computer, which allows a user to communicate with cube server 910. The various system components may communicate via network 940.

Web client 930 may include any device (e.g., personal computer) which communicates via any network, for example such as those discussed herein. Web client 930 may include browser applications comprising Internet browsing software installed within a computing unit or a system to conduct online transactions and/or communications. These computing units or systems may take the form of a computer or set of computers, although other types of computing units or systems may be used, including laptops, notebooks, tablets, hand held computers, personal digital assistants, set-top boxes, workstations, computer-servers, main frame computers, mini-computers, PC servers, pervasive computers, network sets of computers, personal computers, such as iPads, iMACs, and MacBooks, kiosks, terminals, point of sale (POS) devices and/or terminals, televisions, or any other device capable of receiving data over a network. A web-client may run Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Apple Safari, or any other of the myriad software packages available for browsing the internet.

Practitioners will appreciate that a web client may or may not be in direct contact with an application server. For example, a web client may access the services of an application server through another server and/or hardware component, which may have a direct or indirect connection to an Internet server. For example, a web client may communicate with an application server via a load balancer. In various embodiments, access is through a network or the Internet through a commercially-available web-browser software package.

As those skilled in the art will appreciate, a web client may include but is not limited to an operating system (e.g., Windows NT, 95/98/2000/CE/Mobile, OS2, UNIX, Linux, Solaris, MacOS, PalmOS, etc.) as well as various conventional support software and drivers typically associated with computers. A web client may include but is not limited to any suitable personal computer, network computer, workstation, personal digital assistant, cellular phone, smart phone, minicomputer, mainframe or the like. A web client can be in a home or business environment with access to a network. In various embodiments, access is through a network or the Internet through a commercially available web-browser software package. A web client may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). A web client may implement several application layer protocols including http, https, ftp, and sftp.

Network 940 may include any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant (e.g., iPhone®, Palm Pilot®, Blackberry®, cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network is in the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS AND PROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999); DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IP CLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THE DEFINITIVE GUIDE (2002), the contents of which are hereby incorporated by reference.

The various system components may be independently, separately or collectively suitably coupled to the network via data links which includes, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods, see, e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which is hereby incorporated by reference. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.

Web client 930 may comprise any device capable of interacting with Network 940. In various embodiments, web client 930 may comprise a personal computer. However, in various embodiments web client 930 may comprise a PDA, laptop, cellular phone, GPS device, car navigation system, or any other device. Various types of web clients are described in further detail herein.

Any communication, transmission and/or channel discussed herein may include any system or method for delivering content (e.g. data, information, metadata, etc), and/or the content itself. The content may be presented in any form or medium, and in various embodiments, the content may be delivered electronically and/or capable of being presented electronically. For example, a channel may comprise a website, a uniform resource locator (“URL”), a document (e.g., a Microsoft Word document, a Microsoft Excel document, an Adobe .pdf document, etc.), an “ebook,” an “emagazine,” an application or microapplication (as described below), an SMS or other type of text message, an email, facebook, twitter, MMS and/or other type of communication technology. In various embodiments, a channel may be hosted or provided by a data partner. In various embodiments, the distribution channel and/or the may comprise at least one of a merchant website, a social media website, affiliate or partner websites, an external vendor, a mobile device communication, social media network and/or location based service. Distribution channels may include at least one of a merchant website, a social media site, affiliate or partner websites, an external vendor, and a mobile device communication. Examples of social media sites include Facebook®, Foursquare®, Twitter®, MySpace®, LinkedIn®, and the like. Moreover, examples of mobile device communications include texting, email, and mobile applications for smartphones.

In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.

For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system.

The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the system. As those skilled in the art will appreciate, user computer may include an operating system (e.g., Windows NT, Windows 95/98/2000, Windows XP, Windows Vista, Windows 7, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers.

The present system or any part(s) or function(s) thereof may be implemented using hardware, software or a combination thereof and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed by embodiments were often referred to in terms, such as matching or selecting, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein. Rather, the operations may be machine operations. Useful machines for performing the various embodiments include general purpose digital computers or similar devices.

In fact, in various embodiments, the embodiments are directed toward one or more computer systems capable of carrying out the functionality described herein. The computer system includes one or more processors. The processor is connected to a communication infrastructure (e.g., a communications bus, cross over bar, or network). Various software embodiments are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement various embodiments using other computer systems and/or architectures. Computer system can include a display interface that forwards graphics, text, and other data from the communication infrastructure (or from a frame buffer not shown) for display on a display unit.

Computer system also includes a main memory, such as for example random access memory (RAM), and may also include a secondary memory. The secondary memory may include, for example, a hard disk drive and/or a removable storage drive, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive reads from and/or writes to a removable storage unit in a well known manner Removable storage unit represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive. As will be appreciated, the removable storage unit includes a computer usable storage medium having stored therein computer software and/or data.

In various embodiments, secondary memory may include other similar devices for allowing computer programs or other instructions to be loaded into computer system. Such devices may include, for example, a removable storage unit and an interface. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read only memory (EPROM), or programmable read only memory (PROM)) and associated socket, and other removable storage units and interfaces, which allow software and data to be transferred from the removable storage unit to computer system.

Computer system may also include a communications interface. Communications interface allows software and data to be transferred between computer system and external devices. Examples of communications interface may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface are in the form of signals which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface. These signals are provided to communications interface via a communications path (e.g., channel). This channel carries signals and may be implemented using wire, cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, wireless and other communications channels.

The terms “computer program medium” and “computer usable medium” are used to generally refer to media such as removable storage drive and a hard disk installed in hard disk drive. These computer program products provide software to computer system.

Computer programs (also referred to as computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via communications interface. Such computer programs, when executed, enable the computer system to perform the features as discussed herein. In particular, the computer programs, when executed, enable the processor to perform the features of various embodiments. Accordingly, such computer programs represent controllers of the computer system.

In various embodiments, software may be stored in a computer program product and loaded into computer system using removable storage drive, hard disk drive or communications interface. The control logic (software), when executed by the processor, causes the processor to perform the functions of various embodiments as described herein. In various embodiments, hardware components such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).

In various embodiments, the server may include application servers (e.g. WEB SPHERE, WEB LOGIC, JBOSS). In various embodiments, the server may include web servers (e.g. APACHE, IIS, GWS, SUN JAVA SYSTEM WEB SERVER).

In various embodiments, components, modules, and/or engines of system 900 may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a Palm mobile operating system, a Windows mobile operating system, an Android Operating System, Apple iOS, a Blackberry operating system and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.

“Cloud” or “Cloud computing” includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include location-independent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing at http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc (last visited Feb. 4, 2011), which is hereby incorporated by reference in its entirety.

As used herein, “transmit” may include sending electronic data from one system component to another over a network connection. Additionally, as used herein, “data” may include encompassing information such as commands, queries, files, data for storage, and the like in digital or any other form.

The system contemplates uses in association with web services, utility computing, pervasive and individualized computing, security and identity solutions, autonomic computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing and/or mesh computing.

Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (Armonk, N.Y.), various database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Wash.), MySQL by MySQL AB (Uppsala, Sweden), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out (“I/O”) bottlenecks.

More particularly, a “key field” partitions the database according to the high-level class of objects defined by the key field. For example, certain types of data may be designated as a key field in a plurality of related data tables and the data tables may then be linked on the basis of the type of data in the key field. The data corresponding to the key field in each of the linked data tables is preferably the same or of the same type. However, data tables having similar, though not identical, data in the key fields may also be linked by using AGREP, for example. In accordance with various embodiments, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); Binary Large Object (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.

In various embodiments, the ability to store a wide variety of information in different formats is facilitated by storing the information as a BLOB. Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction instrument or external to but affiliated with the financial transaction instrument. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with the financial transaction instrument by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first party, a second data set which may be stored may be provided by an unrelated second party, and yet a third data set which may be stored, may be provided by an third party unrelated to the first and second party. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data that also may be distinct from other subsets.

As stated above, in various embodiments, the data can be stored without regard to a common format. However, in various embodiments, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data onto the financial transaction instrument. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header,” “header,” “trailer,” or “status,” herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set; e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein.

The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified users may be permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate.

The data, including the header or trailer may be received by a stand alone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in various embodiments, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the transaction instrument user at the stand alone device, the appropriate option for the action to be taken. The system may contemplate a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the transaction instrument in relation to the appropriate data.

One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.

Encryption may be performed by way of any of the techniques now available in the art or which may become available—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), and symmetric and asymmetric cryptosystems.

The computing unit of the web client may be further equipped with an Internet browser connected to the Internet or an intranet using standard dial-up, cable, DSL or any other Internet protocol known in the art. Transactions originating at a web client may pass through a firewall in order to prevent unauthorized access from users of other networks. Further, additional firewalls may be deployed between the varying components of ACS to further enhance security.

The computers discussed herein may provide a suitable website or other Internet-based graphical user interface which is accessible by users. In various embodiments, the Microsoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), and Microsoft SQL Server, are used in conjunction with the Microsoft operating system, Microsoft NT web server software, a Microsoft SQL Server database system, and a Microsoft Commerce Server. Additionally, components such as Access or Microsoft SQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In various embodiments, the Apache web server is used in conjunction with a Linux operating system, a MySQL database, and the Perl, PHP, and/or Python programming languages.

Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term “web page” as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, Java applets, JavaScript, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous Javascript And XML), helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL (http://yahoo.com/stockquotes/ge) and an IP address (123.56.789.234). The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communications means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art, and are covered in many standard texts. See, e.g., ALEX NGHIEM, IT WEB SERVICES: A ROADMAP FOR THE ENTERPRISE (2003), hereby incorporated by reference.

Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WebSphere MQTM (formerly MQSeries) by IBM, Inc. (Armonk, N.Y.) is an example of a commercially available middleware product. An Enterprise Service Bus (“ESB”) application is another example of middleware.

Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.

The system and method may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, Java, JavaScript, VBScript, Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly, PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “Java Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.

As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, a processing apparatus executing upgraded software, a stand alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, any portion of the system or a module may take the form of a processing apparatus executing code, an internet based embodiment, an entirely hardware embodiment, or an embodiment combining aspects of the internet, software and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.

The system and method is described herein with reference to screen shots, block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various embodiments. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of windows, webpages, web forms, popup windows, prompts and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or windows but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se. Stated another way, the meaning of the term “non-transitory computer-readable medium” and “non-transitory computer-readable storage medium” should be construed to exclude only those types of transitory computer-readable media which were found in In Re Nuijten to fall outside the scope of patentable subject matter under 35 U.S.C. §101.

Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. Reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to ‘at least one of A, B, and C’ or ‘at least one of A, B, or C’ is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the disclosure includes a method, it is contemplated that it may be embodied as computer program instructions on a tangible computer-readable carrier, such as a magnetic or optical memory or a magnetic or optical disk. All structural, chemical, and functional equivalents to the elements of the above-described exemplary embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the present disclosure, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. 

The invention claimed is:
 1. A computer-implemented method comprising: generating, by a computer-based system for multi-angle videos, a multi-angle video object (“MAV”); displaying, by the computer-based system, a first video on a first face of the MAV, wherein the first video comprises a first angle of an object; displaying, by the computer-based system, a second video on a second face of the MAV, wherein the second video comprises a second angle of the object; and simultaneously playing, by the computer-based system, the first video on the first face and the second video on the second face; wherein the MAV is rotatable between the first face and the second face.
 2. The method of claim 1, further comprising synchronizing, by the computer-based system, the first video and the second video.
 3. The method of claim 1, wherein the MAV comprises a cube.
 4. The method of claim 3, further comprising: displaying, by the computer-based system, a third video on a third face of the MAV; displaying, by the computer-based system, a fourth video on a fourth face of the MAV; displaying, by the computer-based system, a fifth video on a fifth face of the MAV; and displaying, by the computer-based system, a sixth video on a sixth face of the MAV.
 5. The method of claim 4, wherein the third video comprises a third angle of the object, and wherein the fourth video comprises a fourth angle of the object.
 6. The method of claim 1, further comprising rotating, by the computer-based system, the MAV from the first face to the second face.
 7. The method of claim 1, further comprising transmitting, by the computer-based system, the MAV to a web client.
 8. The method of claim 1, wherein the generating the MAV comprises receiving a plurality of videos, wherein the MAV comprises a face for each video in the plurality of videos.
 9. The method of claim 1, wherein the first face of the MAV comprises a first side, wherein the first side is not connected to any other faces of the MAV.
 10. The method of claim 1, further comprising adjusting, by the computer-based system, a brightness of the first video to be consistent with a brightness of the second video.
 11. The method of claim 1, further comprising desynchronizing, by the computer-based system, the first video and the second video.
 12. The method of claim 1, further comprising time-shifting, by the computer-based system, the first video.
 13. The method of claim 1, wherein the MAV comprises a point-of-view perspective.
 14. The method of claim 1, further comprising partially rotating, by the computer-based system, the MAV such that the first video and the second video may be viewed simultaneously.
 15. The method of claim 1, further comprising manipulating the MAV with a smartphone.
 16. A system, comprising: a multi-angle video processor, a tangible, non-transitory memory configured to communicate with the processor, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising: generating, by the processor, a multi-angle video object (“MAV”); displaying, by the processor, a first video on a first face of the MAV, wherein the first video comprises a first angle of an object; displaying, by the processor, a second video on a second face of the MAV, wherein the second video comprises a second angle of the object; and simultaneously playing, by the processor, the first video on the first face and the second video on the second face; wherein the MAV is rotatable between the first face and the second face.
 17. The system of claim 16, wherein the operations further comprise synchronizing, by the processor, the first video and the second video.
 18. The system of claim 16, wherein the MAV comprises a cube.
 19. The system of claim 18, wherein the operations further comprise: displaying, by the processor, a third video on a third face of the MAV; displaying, by the processor, a fourth video on a fourth face of the MAV; displaying, by the processor, a fifth video on a fifth face of the MAV; and displaying, by the processor, a sixth video on a sixth face of the MAV.
 20. The system of claim 16, wherein the operations further comprise rotating, by the processor, the MAV from the first face to the second face.
 21. The system of claim 16, wherein the operations further comprise manipulating the MAV with a smartphone.
 22. An article of manufacture including a tangible, non-transitory computer-readable storage medium having computer-executable instructions stored thereon that, in response to execution by a computer-based system for multi-angle videos, cause the computer-based system to perform operations comprising: generating, by the computer-based system, a multi-angle video object (“MAV”); displaying, by the computer-based system, a first video on a first face of the MAV, wherein the first video comprises a first angle of an object; displaying, by the computer-based system, a second video on a second face of the MAV, wherein the second video comprises a second angle of the object; and simultaneously playing, by the computer-based system, the first video on the first face and the second video on the second face; wherein the MAV is rotatable between the first face and the second face.
 23. The article of manufacture of claim 22, wherein the operations further comprise synchronizing, by the processor, the first video and the second video.
 24. The article of manufacture of claim 22, wherein the MAV comprises a cube.
 25. The article of manufacture of claim 24, wherein the operations further comprise: displaying, by the processor, a third video on a third face of the MAV; displaying, by the processor, a fourth video on a fourth face of the MAV; displaying, by the processor, a fifth video on a fifth face of the MAV; and displaying, by the processor, a sixth video on a sixth face of the MAV.
 26. The article of manufacture of claim 22, wherein the operations further comprise rotating, by the processor, the MAV from the first face to the second face.
 27. The article of manufacture of claim 22, wherein the operations further comprise manipulating the MAV with a smartphone. 